Audio assisted enrollment

ABSTRACT

The present disclosure generally relates techniques for audio-assisted enrollment of biometric features. In some embodiments, methods and devices for assisting users with enrollment of biometric features, using spatial audio cues, are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application Ser. No. 62/739,119, titled “AUDIO ASSISTED ENROLLMENT,” filed Sep. 28, 2018. The contents of these applications are hereby incorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces, and more specifically to techniques for audio-assisted enrollment of biometric features.

BACKGROUND

Humans can locate sounds in three dimensions (above and below, front and rear, and side to side). Different techniques can be used to modify audio such that a listener perceives the audio that a device creates as coming from a particular point in space. The listener's perception can be used to guide user input, including user input during a biometric enrollment process.

BRIEF SUMMARY

Some techniques for biometric enrollment (e.g., enrollment of a user's face) using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may lead to user-error. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for biometric enrollment. Such methods and interfaces optionally complement or replace other methods for biometric enrollment. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power (e.g., by reducing power consumption by processor(s) and display(s) of the devices) and increase the time between battery charges.

In accordance with some embodiments, a method performed at an electronic device having one or more biometric sensors, and operably connected to a first speaker and a second speaker is described. The method includes: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.

In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having one or more biometric sensors, and operably connected to a first speaker and a second speaker. The one or more programs including instructions for: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; and while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.

In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having one or more biometric sensors, and operably connected to a first speaker and a second speaker. The one or more programs including instructions for: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; and while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.

In accordance with some embodiments, an electronic device including: one or more biometric sensors; one or more processors operably connected to a first speaker and second speaker; and memory storing one or more programs configured to be executed by the one or more processors is described. The one or more programs including instructions for: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; and while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.

In accordance with some embodiments, an electronic device is described. The electronic device include: one or more biometric sensors; one or more processors operably connected to a first speaker and a second speaker; means for producing audio in a first audio production mode, while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; means for detecting, while the electronic device remains in the first audio production mode, a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; means for storing, while the electronic device remains in the first audio production mode and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria, first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and means for producing, while the electronic device remains in the first audio production mode and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria, audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.

Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

Thus, devices are provided with faster, more efficient methods and interfaces for audio-assisted enrollment of biometric features, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for audio-assisted enrollment of biometric features.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with some embodiments.

FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

FIGS. 6A-6K illustrate exemplary techniques for audio-assisted biometric enrollment, in accordance with some embodiments.

FIGS. 7A-7D illustrate exemplary techniques for audio-assisted biometric enrollment, in accordance with some embodiments.

FIGS. 8A-8C illustrate exemplary techniques for audio-assisted biometric enrollment, in accordance with some embodiments.

FIGS. 9A-9C is a flow diagram illustrating a method for audio-assisted biometric enrollment in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for audio-assisted enrollment of one or more biometric features, such as a user's face or a user's eye (e.g., iris). For example, spatial audio can provide users with contextual awareness of the state of the electronic device, particularly the state of a biometric enrollment process of the electronic device. Such techniques can reduce the cognitive burden on a user while enrolling biometric features, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs or enrollment attempts.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for managing event notifications. FIGS. 6A-6K, 7A-7D, and 8A-8C illustrate exemplary user interfaces for audio-assisted enrollment of one or more biometric features. FIGS. 9A-9C is a flow diagram illustrating methods of audio-assisted enrollment of one or more biometric features in accordance with some embodiments. The user interfaces in FIGS. 6A-6K, 7A-7D, and 8A-8C are used to illustrate the processes described below, including the processes in FIGS. 9A-9C.

Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that the user's image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor 175 is located on the back of device, or on the back and the front of the device 100. In some embodiments, the position of depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor 175 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is, optionally, coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 optionally performs as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact         list);     -   Telephone module 138;     -   Video conference module 139;     -   E-mail client module 140;     -   Instant messaging (IM) module 141;     -   Workout support module 142;     -   Camera module 143 for still and/or video images;     -   Image management module 144;     -   Video player module;     -   Music player module;     -   Browser module 147;     -   Calendar module 148;     -   Widget modules 149, which optionally include one or more of:         weather widget 149-1, stocks widget 149-2, calculator widget         149-3, alarm clock widget 149-4, dictionary widget 149-5, and         other widgets obtained by the user, as well as user-created         widgets 149-6;     -   Widget creator module 150 for making user-created widgets 149-6;     -   Search module 151;     -   Video and music player module 152, which merges video player         module and music player module;     -   Notes module 153;     -   Map module 154; and/or     -   Online video module 155.

Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),         such as cellular and Wi-Fi signals;     -   Time 404;     -   Bluetooth indicator 405;     -   Battery status indicator 406;     -   Tray 408 with icons for frequently used applications, such as:         -   Icon 416 for telephone module 138, labeled “Phone,” which             optionally includes an indicator 414 of the number of missed             calls or voicemail messages;         -   Icon 418 for e-mail client module 140, labeled “Mail,” which             optionally includes an indicator 410 of the number of unread             e-mails;         -   Icon 420 for browser module 147, labeled “Browser;” and         -   Icon 422 for video and music player module 152, also             referred to as iPod (trademark of Apple Inc.) module 152,             labeled “iPod;” and     -   Icons for other applications, such as:         -   Icon 424 for IM module 141, labeled “Messages;”         -   Icon 426 for calendar module 148, labeled “Calendar;”         -   Icon 428 for image management module 144, labeled “Photos;”         -   Icon 430 for camera module 143, labeled “Camera;”         -   Icon 432 for online video module 155, labeled “Online             Video;”         -   Icon 434 for stocks widget 149-2, labeled “Stocks;”         -   Icon 436 for map module 154, labeled “Maps;”         -   Icon 438 for weather widget 149-1, labeled “Weather;”         -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”         -   Icon 442 for workout support module 142, labeled “Workout             Support;”         -   Icon 444 for notes module 153, labeled “Notes;” and         -   Icon 446 for a settings application or module, labeled             “Settings,” which provides access to settings for device 100             and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including process 900 (FIGS. 9A-9C). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.

An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.

As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:

-   -   an active application, which is currently displayed on a display         screen of the device that the application is being used on;     -   a background application (or background processes), which is not         currently displayed, but one or more processes for the         application are being processed by one or more processors; and     -   a suspended or hibernated application, which is not running, but         has state information that is stored in memory (volatile and         non-volatile, respectively) and that can be used to resume         execution of the application.

As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.

Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6K, 7A-7D, and 8A-8C illustrate exemplary techniques for audio-assisted biometric enrollment, in accordance with some embodiments. The techniques in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9C. In general, the embodiments of 6A-6K, 7A-7D, and 8A-8C illustrate the use of spatial audio techniques (e.g., techniques for simulating and/or controlling sound localization (e.g., as perceived by a user)) so as to simulate audio being produced from various locations, including locations that are distinct from the location of the electronic device outputting the audio. In some embodiments, the spatial audio is produced based on one or more functions such as a head-related transfer function, an interaural time difference function, and a cross cancellation function. In some embodiments, the spatial audio is produced based on one or more environmental (e.g., ambient noise), device contextual (e.g., orientation of the device, movement of the device, or current audio playback status of the device), or user-specific parameters (e.g., user orientation with respect to the device, user positioning/distance from the device).

FIGS. 6A-6G depict (in the upper portion) device 600, a smart phone, displaying a biometric enrollment interface 604 on display 602. Device 600 further includes a biometric sensor 606, a first speaker 608 and a second speaker 610, positioned along the bottom edge of device 600. In some embodiments, device 600 further includes one or more features of device 100, device 300, or device 500.

In some embodiments, biometric sensor 606 includes one or more cameras such as a visible light camera, a depth camera, such as an infrared camera, a thermographic camera, or a combination thereof. In some examples, the device further includes a light-emitting device (e.g., light projector), such an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the subject during capture of the image by a visible light camera and a depth camera (e.g., an IR camera) and the information from the depth camera and the visible light camera are used to determine a depth map of different portions of subject captured by the visible light camera. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint.) In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction. In some embodiments, the lighting effects described herein are displayed using disparity information from two cameras (e.g., two visual light cameras) for rear facing images and using depth information from a depth camera combined with image data from a visual light camera for front facing images (e.g., selfie images). In some embodiments, the same user interface is used when the two visual light cameras are used to determine the depth information and when the depth camera is used to determine the depth information, providing the user with a consistent experience, even when using dramatically different technologies to determine the information that is used when generating the lighting effects. In some embodiments, while displaying the camera user interface with one of the lighting effects applied, the device detects selection of a camera switching affordance and switches from the front facing cameras (e.g., a depth camera and a visible light camera) to the rear facing cameras (e.g., two visible light cameras that are spaced apart from each other) (or vice versa) while maintaining display of the user interface controls for applying the lighting effect and replacing display of the field of view of the front facing cameras to the field of view of the rear facing cameras (or vice versa).

Additionally, FIGS. 6A-6G depicts (in the bottom portion) an overhead view 601 of user 603, interacting with device 600, as well as a top view of device 600, at the same point in time. As seen in the overhead view, user 603 is positioned a distance D from device 600, with the display of device 600 directly facing user 603. In some embodiments, device 600 determines distance D using data from at least a depth camera of biometric sensor 606. Overhead view 601 is not part of any user interface of device 600. Similarly, visual elements displayed outside of the display 602 of device 600 are not part of the displayed user interface, but are illustrated to provide the reader with a better understanding of the techniques described herein.

At FIG. 6A, device 600 displays, on display 602, biometric enrollment interface 604, which is a user interface for facilitating biometric enrollment of one or more portions of user 603 (e.g., for later use in biometric enrollment techniques). Biometric enrollment interface 604 includes a user image 612 a, a progress meter 614, which includes progress ticks 614 a and 614 b that depict the status of biometric enrollment. In FIG. 6A, upper (ticks 614 b) and lower portions of progress meter 614 are darkened, indicating that certain portions of the user's face (e.g., upper and lower portions) of the user's face have already been successfully captured as part of the overall enrollment process. In contrast, left (ticks 614 a) and right portions of progress meter 614 remain undarkened/unfilled, indicating that the left and right portions of the user's face still remain uncaptured. Biometric interface 604 further includes text 616 to guide the user in the actions needed to complete the biometric enrollment process.

While displaying the user interface seen in FIG. 6A, device 600 detects that the user's face 605 is in an orientation relative to the biometric sensor 606 that does not meet enrollment criteria (e.g., face 605 is not orientated so as to permit capture of the right portion of the user's face). Device 600 proceeds to produce both audio and visual cues to further guide the user in the process of biometric authentication, as seen in FIG. 6B. In some embodiments, device 600 produces audio and visual cues only after device 600 detects the user maintaining an orientation that that does not meet enrollment criteria for at least a predetermined period of time (e.g., 5 seconds).

At FIG. 6B, device 600 displays, on display 602, movement prompt 618 a (e.g., an animation guiding user 603 to turn his head to the left so as to permit capture of the right portion of his face) along with text 616 b. Device 600 also outputs directional haptics 622 a, via one or more haptic actuators. At the same time, device 600 outputs, in a (e.g., first) audio production mode, spatial audio 620 a that is initially calculated to simulate audio being produced from a location D_(I) (an initial location calculated by the device) that is to the left of the actual position of device 600, including the position of integrated speakers 608 and 610 of device 600, and at an angle ΘD_(I) based on a center line between user 603 and device 600, as seen in overhead view 601. In some embodiments, location D_(I) is determined based on a target orientation of the user's face that would allow for capture of a portion (e.g., a right portion) of the user's face required for successful biometric enrollment. However, due to one or more environmental (e.g., ambient noise), device contextual (e.g., orientation of the device, movement of the device, or current audio playback status of the device), or user-specific factors (e.g., user orientation with respect to the device, user positioning/distance from the device, specific physiological characteristics of user 603 (e.g., the user's ear and/or head shape)), user 603 localizes audio 620 a as being produced from a location U_(I) (an initial location perceived by the user) that is spaced apart from location D_(I) and at an angle ΘU_(I) based on a center line between user 603 and device 600. As seen in FIG. 6B, angle ΘU_(I) is less than angle ΘD_(I).

At FIG. 6C, user 603 turns his head to the left so as to align the centerline of his head with location U_(I), based on the user's perception of the localization of audio 620 a. Device 600 detects, via biometric sensor 606, that the orientation of the user's face has changed with respect to device 600 and, in response, updates display of user image 612 b to reflect the change in orientation and partially fills ticks 614 a indicating partial progress towards enrolling a corresponding portion (e.g., the right portion) of the user's face. However, because angle ΘU_(I) is less than angle ΘD_(I), the user's face is not properly orientated so as to complete capture of the right portion of the user's face. In some embodiments, after detecting (e.g., via the biometric sensor 606) that the user has maintained a repositioned orientation (e.g., after the production of audio 620 a) that does not align the user's face with ΘD_(I), thereby meeting feedback criteria, device 600 adjusts one or more characteristics of the audio output to produce adjusted audio 620 b, which is calculated to simulate audio being produced from a location D_(A) (which is the same location as position D_(I)) that will align with the localization perceived by user 603 at location U_(A). In some embodiments, audio 620 b is determined based, at least in part, on the difference between angle ΘD_(I) and angle ΘU_(I), thereby adjusting for/factoring in user 603's specific physiological characteristics affecting the perception of audio localization or other factors (e.g., environmental factors) that affect the user's perceived localization. In some embodiments, device 600 stores the information used to adjust the spatial audio based as calibration data for use in generating subsequent spatial audio.

At FIG. 6D, device 600, in a (e.g., third) audio production mode, is producing adjusted audio 620 b, which is calculated to be at position D_(A) and is perceived by the user to be localized at position U_(A) and user 603 has oriented his head so that the centerline of his head is aligned with position D_(A)/U_(A). While device 600 is producing audio 620 b, device 600 detects, via biometric sensor 606, that the user's head is oriented such that the centerline of the user's head is at an angle ΘD_(A)/ΘU_(A). In accordance with the orientation of the right portion of the user's face meeting enrollment criteria (e.g., being at a required angle with respect to biometric sensor 606), device 600 stores image data (e.g., visible light image data and depth map image data) corresponding to the right portion of the user's face, captured using the biometric sensor 606. Further in accordance with the orientation of the right portion of the user's face meeting enrollment criteria, device 600 fills in ticks 614 a and displays text 616 c, and outputs haptics 622 b (e.g., haptics that are different (e.g., stronger and non-directional) than haptics 622 a), indicating that the right portion of the user's face has successfully been captured. Device 600 updates display of user image 612 c, reflecting the detected change in orientation. In some embodiments, further in accordance with the orientation of the right portion of the user's face meeting enrollment criteria, device 600 outputs, in a (e.g., second) audio production mode, spatial audio that is (initially) calculated to simulate audio being produced from a location that is to the right of the actual position of device 600 to guide user 603 to orient his face in a position to allow capture and enrollment of the left portion of the user's face. In some embodiments, the spatial audio is produced subsequent to, but not in accordance with, the orientation of the right portion of the user's face meeting enrollment criteria. For example, the spatial audio is produced after device 600 detects the user maintaining an orientation that that does not meet enrollment criteria (e.g., enrollment criteria for the left portion of the user's face) for at least a predetermined period of time (e.g., 5 seconds) after the right portion of the user's face has successfully been captured.

At FIG. 6E, device 600 displays, on display 602, movement prompt 618 b (e.g., an animation guiding user 603 to turn his head to the right so as to permit capture of the left portion of his face) along with text 616 d. Device 600 also outputs directional haptics 622 b, via one or more haptic actuators. At the same time, device 600 outputs, in a (second) audio production mode, spatial audio 620 c that is calculated to simulate audio being produced from a location D_(I) (an initial location calculated by the device) that is to the right of the actual position of device 600 (including the position of integrated speakers 608 and 610 of device 600) and at an angle ΘD_(I) based on a center line between user 603 and device 600, as seen in overhead view 601. In the embodiment of FIG. 6E, device 600 uses calibration data obtained from the adjustment of spatial audio 620 a to generate spatial audio 620 b to generate spatial audio 620 c. As a result, spatial audio 620 c is perceptually localized by user 603 at location U_(I) that corresponds to location D_(I) (e.g., corresponds without the need for further adjustment).

At FIG. 6F, device 600 detects, via biometric sensor 606, user 603 turning his head to the right (e.g., turning his head so as to orient on the perceived location of audio 620 c). In response to the detected change in orientation, device 600 updates display of user image 612 d to reflect the change in orientation and partially fills ticks 614 b indicating partial progress towards enrolling a corresponding portion (e.g., the left portion) of the user's face. Device 600 continues to produce audio 620 c and directional haptics 622 c.

Just prior to FIG. 6G, device 600, remains in the second audio production mode and continues to produce spatial audio 620 c. At FIG. 6G, while device 600 is producing audio 620 c, device 600 detects, via biometric sensor 606, that the user's head is oriented such that the centerline of the user's head is at an angle ΘD_(A)/ΘU_(A). In accordance with the orientation of the left portion of the user's face meeting enrollment criteria (e.g., being at a required angle with respect to biometric sensor 606), device 600 stores image data (e.g., visible light image data and depth map image data) corresponding to the left portion of the user's face, captured using the biometric sensor 606. Further in accordance with the orientation of the left portion of the user's face meeting enrollment criteria, device 600 fills in ticks 614 b and displays text 616 d, and outputs haptics 622 d (e.g., non-directional haptics that are different than haptics 622 c) indicating that the left portion of the user's face has successfully been captured. Device 600 updates display of user image 612 e, reflecting the detected change in orientation.

At FIG. 6H, device 600 determines that overall enrollment criteria are met (e.g., all required portions of the user's face have been successfully captured) and displays text 616 e, signaling the successful completion of biometric enrollment of the user's face.

FIG. 6I depicts the user interacting with device 600 at a point in time after successful completion of biometric enrollment of the user's face (e.g., after FIG. 6H). FIG. 6J depicts the user interface of device 600, as user 603 interacts with device 600. As shown in FIG. 6J, device 600 displays a lock image 624, indicating that device 600 is in a locked state (e.g., a state in which one or functions of the device is inaccessible (e.g., inaccessible until authentication is provided). Device 600 determines that authentication criteria are met (e.g., detects the presence of user 603 via biometric sensor 606, detects a change in orientation of the device (e.g., from lowered position to a raised position), or detects a touch on touch-sensitive display 602) and performs a biometric authentication check using data captured by biometric sensor 606.

At FIG. 6K, device 600 determines that data captured by biometric sensor 606 matches stored, authorized biometric data (e.g., user 603 is confirmed to be the same user that performed the biometric enrollment of FIGS. 6A-6H) and unlocks, as indicated by the updated display of lock image 624 b. User 603 is now free to access previously inaccessible functions of device 600.

FIGS. 7A-7D depicts a biometric enrollment process that shares some similarities with the biometric enrollment process of FIGS. 6A-6H. In contrast to user 603 of FIGS. 6A-6H, user 703 of FIGS. 7A-7D is wearing wireless headphones 707, which are operatively connected to device 600 (e.g., via Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques). Device 600 detects the connection to headphones 707 and configures audio (including spatial audio associated with biometric enrollment) to be outputted via the headphones 707, rather than device speakers 608 and 610. In the embodiment of FIGS. 7A-7D, headphones 707 include a plurality of speakers and one or more physiological sensors that determine characteristics (e.g., the shape of the user's ears and/or head) of user 703 that affect the perceptual localization of the spatial audio and transmits information to device 600 that can be used to calibrate spatial audio signals. Headphones 707 also includes one or more accelerometers configured to detect changes in orientation and position of the headphones 707 and transmit information to device 600 that can be used to determine changes in orientation and position of the headphones, with respect to the position of device 600.

While displaying the user interface seen in FIG. 7A, which includes biometric enrollment interface 704 includes a user image 712 a, text 716 a, a progress meter 714, which includes progress ticks 714 a and 714 b that depict the status of biometric enrollment, device 600 detects that the user's face 705 is in an orientation relative to the biometric sensor 606 that does not meet enrollment criteria (e.g., face 605 is not orientated so as to permit capture of the left portion of the user's face). Device 600 proceeds to produce both audio and visual cues to further guide the user in the process of biometric authentication, as seen in FIG. 7B. In some embodiments, device 600 produces audio and visual cues only after device 600 detects the user maintaining an orientation that that does not meet enrollment criteria for at least a predetermined period of time (e.g., 5 seconds).

At FIG. 7B, device 600 displays, on display 602, movement prompt 718 a (e.g., an animation guiding user 703 to turn his head to the right so as to permit capture of the left portion of his face) along with text 716 b. Device 600 also outputs directional haptics 722 a, via one or more haptic actuators. At the same time, device 600 outputs, in a (e.g., first) audio production mode, spatial audio 720 a that is calculated to simulate audio being produced from a location D_(I) (an initial location calculated by the device) that is to the right of the actual position of device 600 and at an angle ΘD_(I) based on a center line between user 703 and device 600, as seen in overhead view 701. In some embodiments, location D_(I) is determined based on a target orientation of the user's face that would allow for capture of a portion (e.g., a left portion) of the user's face required for successful biometric enrollment. In the embodiment of FIG. 7B, device 600 uses calibration data obtained from the physiological sensors of headphones 707 to generate spatial audio 720 a. As a result, spatial audio 720 a is perceptually localized by user 703 at location U_(I) that corresponds to location D_(I) (e.g., corresponds without the need for further adjustment).

At FIG. 7C, device 600 detects, via biometric sensor 606, user 703 turning his head to the right (e.g., turning his head so as to orient on the perceived location of audio 720 a). In response to the detected change in orientation, device 600 updates display of user image 712 b to reflect the change in orientation and partially fills ticks 714 b indicating partial progress towards enrolling a corresponding portion (e.g., the left portion) of the user's face. Device 600 continues to produce audio 720 a and directional haptics 714 a. As shown in FIG. 7C, because user 703 is wearing headphones 707, the change in the orientation of the user's head with respect to device 600 causes a corresponding change in the orientation of headphones 707 with respect to device 600. Consequently, spatial audio 720 a would be perceptually localized by the user at position U_(I), which is further to the right of position U_(I) of FIG. 7A, prior to the change in orientation of the user's head. As a result, the user's head would be at an angle ΘU_(I), with respect to a center line between user 703 and device 600, that is greater than that of ΘU_(I) of FIG. 7B and that is greater than an optimal angle for enrollment of the left portion of the user's face. To avoid the phenomenon of the simulated position of the spatial audio shifts (e.g., constantly or intermittently shifts) with changes in orientation of the user's head, device 600 adjusts or modulates the spatial audio (e.g., while remaining in the first audio production mode) to produce adjusted spatial audio 720 b. In some embodiments, device 600 adjust the spatial audio based on accelerometer data received from headphones 707 and/or based on data captured via biometric sensor 606, reflecting a change in orientation of the user's head and headphones 707. In FIG. 7C, adjusted spatial audio 720 b simulates audio sourced at a position D_(A) that matches position D_(I) of FIG. 7B. In some embodiments, device 600 continues (e.g., constantly or intermittently) to adjust or modulate the spatial audio as further changes in orientation of the user's head are detected.

At FIG. 7D, device 600 is outputting spatial audio 720 c, an adjusted spatial audio that is perceptually localized by the user as directly in front, while the user's head is oriented at an angle ΘU_(A) that is optimal for biometric capture of the left portion of the user's face. While device 600 is producing audio 720 c, device 600 detects, via biometric sensor 606, that the user's head is oriented such that the centerline of the user's head is at an angle ΘU_(A). In accordance with the orientation of the left portion of the user's face meeting enrollment criteria (e.g., being at a required angle with respect to biometric sensor 606), device 600 stores image data (e.g., visible light image data and depth map image data) corresponding to the left portion of the user's face, captured using the biometric sensor 606. Further in accordance with the orientation of the left portion of the user's face meeting enrollment criteria, device 600 fills in ticks 714 b and displays text 716 c, and outputs haptics 722 b (e.g., haptics that are different (e.g., stronger and non-directional) than haptics 722 a) indicating that the left portion of the user's face has successfully been captured. Device 600 updates display of user image 712 c, reflecting the detected change in orientation. In some embodiments, biometric authentication continues until all required portions of the user's face are enrolled.

FIGS. 8A-8C depicts a biometric enrollment process that shares some similarities with the biometric enrollment processes of FIGS. 6A-6H and FIGS. 7A-7D. Note that in FIGS. 8A-8C, a side view 801 of user 803 interacting with device 600 is provided, rather than an overhead view. User 803 is wearing wireless headphones 707, which are operatively connected to device 600 (e.g., via Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques).

While displaying the user interface seen in FIG. 8A, which includes biometric enrollment interface 804 includes a user image 812 a, text 816 a, a progress meter 814, which includes progress ticks 814 a and 814 b that depict the status of biometric enrollment, device 600 detects that the user's face 805 is in an orientation relative to the biometric sensor 606 that does not meet enrollment criteria (e.g., face 605 is not orientated so as to permit capture of the lower portion of the user's face). Device 600 proceeds to produce both audio and visual cues to further guide the user in the process of biometric authentication, as seen in FIG. 8B. In some embodiments, device 600 produces audio and visual cues only after device 600 detects the user maintaining an orientation that that does not meet enrollment criteria for at least a predetermined period of time (e.g., 5 seconds).

At FIG. 8B, device 600 displays, on display 602, movement prompt 818 a (e.g., an animation guiding user 703 to look upwards so as to permit capture of the lower portion of his face) along with text 816 b. Device 600 also outputs directional haptics 822 a, via one or more haptic actuators. At the same time, device 600 outputs, in a (first) audio production mode, spatial audio 820 a that is calculated to simulate audio being produced from a location D_(I) (an initial location calculated by the device) that above the actual position of device 600 and at an angle ΘD_(I) based on a center line between user 803 and device 600, as seen in side view 801. In some embodiments, location D_(I) is determined based on a target orientation of the user's face that would allow for capture of a portion (e.g., a lower portion) of the user's face required for successful biometric enrollment. In the embodiment of FIG. 8B, device 600 uses calibration data obtained from the physiological sensors of headphones 707 to generate spatial audio 820 a. As a result, spatial audio 820 a is perceptually localized by user 803 at location U_(I) that corresponds to location D_(I) (e.g., corresponds without the need for further adjustment).

At FIG. 8C, device 600 is outputting spatial 820 b (an adjusted spatial audio that is perceptually localized by the user as directly in front, while the user's head is oriented at an angle ΘU_(A) that is optimal for biometric capture of the lower portion of the user's face). While device 600 is producing audio, device 600 detects, via biometric sensor 606, that the user's head is oriented such that the centerline of the user's head is at an angle ΘU_(A). In accordance with the orientation of the lower portion of the user's face meeting enrollment criteria (e.g., being at a required angle with respect to biometric sensor 606), device 600 stores image data (e.g., visible light image data and depth map image data) corresponding to the lower portion of the user's face, captured using the biometric sensor 606. Further in accordance with the orientation of the lower portion of the user's face meeting enrollment criteria, device 600 fills in ticks 814 a and displays text 816 c, and outputs haptics 822 b (e.g., haptics that are different (e.g., stronger and non-directional) than haptics 822 a) indicating that the lower portion of the user's face has successfully been captured. Device 600 updates display of user image 812 b, reflecting the detected change in orientation. In some embodiments, biometric authentication continues until all required portions of the user's face are enrolled.

FIG. 9A-9C is a flow diagram illustrating a method for audio-assisted biometric enrollment using an electronic device in accordance with some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500) with one or more biometric sensors (e.g., 606) and operably connected to a plurality of speakers (e.g., left and right speakers, left and right headphones (e.g., earphones, earbuds)) (e.g., 608, 610, and/or 707). In some embodiments, the electronic device includes one or more biometric sensors that optionally include one or more cameras such as an infrared camera, a thermographic camera, or a combination thereof. In some embodiments, the device further includes a light-emitting device, such as an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the biometric feature (e.g., the face) during capture of biometric data of the biometric features by the one or more biometric sensors.

In accordance with some embodiments, the first speaker (e.g., 608) and second speaker (e.g., 610) are in fixed positions relative to the one or more biometric sensors (e.g., 606).

In accordance with some embodiments, the first speaker and the second speaker are not in a fixed position (e.g., left and right headphones (e.g., earphones or earbuds); e.g., 707) relative to the one or more biometric sensors.

Some operations in method 900 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for providing audio-assisted biometric enrollment. The method reduces the cognitive burden on a user for biometric enrollment, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to enroll a biometric feature faster and more efficiently conserves power and increases the time between battery charges.

The electronic device (e.g., 600), while detecting that a biometric feature (e.g., a face 605) is in a first orientation (e.g., the orientation (e.g., the user's face has tilted upwards) of the biometric feature relative to the one or more biometric sensors is based on the alignment of a face of a user in image data captured by the one or more cameras), relative to the one or more biometric sensors (e.g., 606), that does not meet a first enrollment criteria (e.g., a requirement that the image data includes data corresponding to a first angular view of the face of the user from a first perspective angle (e.g., a right profile perspective of the face, such as when the user's face is tilted to the right)), produces (902) audio in a first audio production mode (e.g., by applying filters). The audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location (e.g., D_(I)) that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker (e.g., audio that is perceived by a user as being produced from a first direction (e.g., to the right of the device) that is not in the direction of the electronic device). Producing audio so as to simulate audio being produced from a first location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker provides the user with improved information as to a target orientation and reduces the inputs needed to complete biometric enrollment. Providing improved audio feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the first location (e.g., D_(I)) is in a direction perpendicular (e.g., vertical direction above or below the user's head) to a plane formed by the first speaker (e.g., 608), the second speaker (e.g., 610), and at least one of the one or more biometric sensors (e.g., 606).

In accordance with some embodiments, the electronic device is operably connected to a third speaker and a fourth speaker (e.g., left and right speakers or speakers 608 and 610) and producing audio in the first audio production mode includes the electronic device determining (904) if the first speaker and second speaker (e.g., speakers of headphones 707) are operable (e.g., speakers are powered on or capable of playing audio), and, in accordance with determining that the first and second speakers are operable, the electronic device foregoes (906) producing audio using the third speaker and the fourth speaker.

In accordance with some embodiments, producing audio in the first audio production mode includes the electronic device foregoing modulating the audio (e.g., not varying the interaural time difference, HRTF, or cross cancellation) of the first speaker (e.g., 608) and the second speaker (e.g., 610) based on a change in position of the biometric feature (e.g., 605) relative to the one or more biometric sensors (e.g., 606).

In accordance with some embodiments, producing audio in the first audio production mode includes, in accordance with a determination that the second orientation (e.g., orientation seen in FIG. 6B) does not meet the first enrollment criteria (e.g., face is not in the right orientation) and in accordance with a determination that a feedback criteria (e.g., second orientation maintained for a period of time) is met, the electronic device producing audio in a third audio production mode (e.g., audio that is perceived by a user as being produced from a third direction (e.g., D_(A)) that is not in the direction of the electronic device or the first direction (e.g., D_(I)) (e.g., where the audio is perceived as being farther to the right of the electronic device)) (In some embodiments, audio produced in the third audio production mode is modified using or more of an HRTF, applying an interaural time difference of audio, or cross cancellation). Audio produced in the third audio production mode is generated so as to simulate audio being produced from a third location (e.g., D_(A)) that is not the location of the one or more biometric sensors (e.g., 606), wherein the third location is different from the first location. Producing adjusted audio so as to simulate audio being produced from a third location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker provides the user with improved information as to a target orientation and reduces the inputs needed to complete biometric enrollment. Doing so when the user is in a second orientation that does not meet the first enrollment criteria further assists the user in achieving an orientation required for biometric enrollment. Providing improved audio feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the electronic device, in accordance with a determination that the second orientation does not meet the first enrollment criteria (e.g., second orientation not maintained for a period of time (e.g., user does not stop moving face towards target orientation)) and in accordance with a determination that the feedback criteria is not met, remains in the first audio production mode (e.g., foregoing transitioning to producing audio in the third audio production mode).

In accordance with some embodiments, the first enrollment criteria includes a target orientation (e.g., determining that the image data includes data corresponding to a first angular view of the face of the user from a first perspective angle (e.g., a right profile perspective of the face, such as when the user's face is tilted to the right)) and the third location (e.g., D_(A)) is determined based on the difference between the target orientation and the second orientation (e.g., the difference between D_(I) and U_(I) of FIG. 6C). (e.g., the electronic device employs a process integral derivative feedback loop where the error value is the delta between the desired head pose).

In accordance with some embodiments, producing audio in the first audio production mode includes the electronic device modulating (908) the audio (e.g., varying the applied interaural time difference, HRTF, or cross cancellation function) of the first speaker (e.g., 608) and second speaker (e.g., 610) so that the audio continues to be generated so as to simulate audio being produced from the first location (e.g., D_(I)), wherein modulating the audio is based on a change in position of the first speaker and second speaker relative (e.g., a headphone/earphone/earbud wearing user tilting head in one direction) to the one or more biometric sensors.

In accordance with some embodiments, producing audio in the first audio production mode includes the electronic device producing (910) a first tactile output (e.g., haptic output; e.g., 622 a) corresponding (e.g., haptic output that indicates the direction of the sound (e.g., sequence of vibrations of a certain count that indicates left while a different number indicates right)) to the first location (e.g., D_(I)). Providing a tactile output that corresponds to the first location (e.g., a location corresponding to an orientation required for biometric enrollment) provides the user with improved information as to a target orientation and reduces the inputs needed to complete biometric enrollment. Providing improved tactile feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the electronic device further includes a display (In some embodiments, the display is a touch-sensitive display. In some embodiments, the display is not a touch sensitive display. In some embodiments, the electronic device, while detecting that a biometric feature (e.g., 605) is in a first orientation, displays (912), on the display, a biometric enrollment interface (e.g., 604). In some embodiments, the displayed biometric enrollment interface is a biometric enrollment interface having one or more features of the biometric enrollment interfaces described in U.S. Patent Application No. 62/557,130, “Implementation Of Biometric Authentication,” filed Sep. 11, 2017, e.g., at paragraphs [0278], [0285]-[0300], [0318]-[0323] and FIGS. 7S and 9R, which is hereby incorporated by reference. In some embodiments, the biometric enrollment interface includes user facial image data displayed within a positioning element. User facial image data may include a user facial image in a live preview of image data captured by the one or more biometric sensor. The biometric enrollment interface may also optionally include an enrollment progress meter (e.g., 614) that surrounds the user facial image and positioning element. The enrollment progress meter is composed of a set of progress elements (e.g., 614 a) that extend radially outward from the user facial image and, in some examples, in a circular pattern. In some embodiments, the displayed biometric enrollment interface includes an orientation guide. In some embodiments, the orientation guide includes a set of curved lines (e.g., crosshairs) that appear to extend out of the plane of the display in a virtual z-dimension, intersecting over the center of the user facial image. In some examples, the orientation guide provides a sense of the three-dimensional orientation of the user's face even though the image is two-dimensional. In this case, the orientation guide assists the user in the biometric enrollment process by making rotations and/or tilts of the user's head relative to the device more visually apparent. Biometric enrollment interface may also include a text prompt (e.g., 616 a), which optionally instructs the user to begin tilting their head, for instance, in a circle to perform enrollment.

In accordance with some embodiments, producing audio in the first audio production mode includes the electronic device displaying, as part of the biometric enrollment interface (e.g., 604), a first visual output (e.g., images on the biometric enrollment interface indicating the direction the user should turn their face for enrolling; 618 c) corresponding to the first location (e.g., the visual output indicates the direction the user should turn their face for enrollment, such as displaying the phrase “turn to the left”). Providing a visual output that corresponds to the first location (e.g., a location corresponding to an orientation required for biometric enrollment) provides the user with improved information as to a target orientation and reduces the inputs needed to complete biometric enrollment. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In some embodiments, the electronic device, further in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria, displays, on the display, a second visual output (e.g., visual feedback that provides the user an indication that the user's face is in the correct position (e.g., displaying the phrase “stop turning”; 616 c)).

In accordance with some embodiments, producing audio in a first audio production mode includes the electronic device detecting, using the one or more biometric sensors, a distance (e.g., 601) the user is from the one or biometric sensors, and determining the first location based on the distance the user is from the one or more biometric sensors.

In accordance with some embodiments, producing audio using the first audio production mode includes the electronic device applying one or more functions selected from the group consisting of: a head-related transfer function, an interaural time difference function, and a cross cancellation function.

In accordance with some embodiments, prior to producing audio in the first audio production mode, the electronic device detects (e.g., using the one or more biometric sensors or a second set of one or more biometric sensors (e.g., a second set of biometric sensors included in headphones worn by the user) a user physical characteristic (e.g., head shape or ear shape). In such embodiments, producing audio in a first audio production mode includes modulating the audio produced in the first audio production mode based on the user physical characteristic.

In accordance with some embodiments, after producing audio in a first audio production mode and while the electronic device remains in the first audio production mode, the electronic device, in accordance with a determination that the second orientation of the biometric feature does not meet the first enrollment criteria (e.g., the user's face is not at the target orientation), continues to produce audio in the first audio production mode.

The electronic device, while remaining in the first audio production mode (e.g., the electronic device remains in the audio production mode even it is not actively producing audio at a given time point), detects (914) a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation (e.g., the user's face is turned to the right).

In accordance with some embodiments, detecting a change in orientation of the biometric feature is based on one or more motion sensors (e.g. inertial measurement unit sensor), wherein the one or more motion sensors are in a fixed position relative to the first speaker and second speaker (e.g., motion sensors integrated into headphones 707). In some embodiments, the change is detected using inertial measurement unit sensors built-in to headphones, earphones, or earbuds.

In accordance with some embodiments, detecting a change in the orientation of the biometric feature is based on data from the one or more biometric sensors (e.g., 606) (e.g. two-dimensional front facing camera, lidar or structured light sensor, or creating a three-dimensional model of the head using depth reconstruction from multiple depth of field images taken in rapid succession).

The electronic device, while remaining (916) in the first audio production mode and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria (e.g., face is in the target orientation), stores (918) (e.g., enrolling the first data for subsequent use in a biometric authentication method) first image data (e.g., data from the face of the user corresponding to an angular view of the user from a perspective angle) corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation (e.g., the user's face is turned to the right). Storing image data corresponding to the biometric feature can provide the user with the ability to use the data for later biometric authentication, improving security. Improving security enhances the operability of the device and makes the user-device interface more secure which, reduces the risk of unauthorized use.

The electronic device, while remaining (916) in the first audio production mode and in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria (e.g., face is in the target orientation), produces (920) audio in a second audio production mode. The audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location (e.g., D_(I) of FIG. 6E) that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker. The first location is different from the second location (e.g., audio that is perceived by a user as being produced from a second direction that is not in the direction of the electronic device or the first direction (e.g., where the audio is perceived as being to the left of the electronic device)).

In accordance with some embodiments, the electronic device, further in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria, produces a second tactile output (e.g., haptic feedback that provides the user an indication that the user's face is in the correct position; e.g., 622 b). In some embodiments, the second tactile output is different than the first tactile output.

In accordance with some embodiments, while the electronic device remains (922) in the second audio production mode (e.g., the electronic device remains in the mode even if it is not actively producing audio at a given time point), the electronic device detects (924) a change in orientation of the biometric feature relative to the one or more biometric sensors from the second orientation to a third orientation (e.g., the user's face is turned to the left). while the electronic device remains (922) in the second audio production mode and in accordance with a determination that the third orientation of the biometric feature meets a second enrollment criteria (e.g., an enrollment criteria different than the first enrollment criteria), the electronic device stores (926) (e.g., enrolling the second data for subsequent use in a biometric authentication method) second image data (e.g., user facial image) corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the third orientation. (e.g., the user's face is turned to the left).

In accordance with some embodiments, the electronic device receives a request to access a restricted function of the device (e.g., a request to unlock the device; e.g., as seen in FIG. 6I). In response to the request to access the restricted function of the device, the electronic device, in accordance with a determination that biometric authentication criteria has been met (e.g., a biometric feature, such as a face, is authenticated by the device) based on biometric data provided by the one or more biometric sensors, providing access to the restricted function of the device (e.g., transition the electronic device from a first visual state (e.g., locked state) to a second visual state (e.g., unlocked state)) and in accordance with a determination that biometric authentication criteria has not been met based on biometric data provided by the one or more biometric sensors, forgoes providing access to the restricted function of the device (e.g., maintain the electronic device in the first visual state (e.g., locked state)).

In accordance with some embodiments, the biometric feature is at least a portion of a face (e.g., 605); and the first image data obtained from the one or more biometric sensors includes biometric data associated with the at least a portion of the face.

In accordance with some embodiments, the first enrollment criteria includes a criterion that is satisfied when the biometric feature is oriented relative to the one or more sensors in a predetermined manner (e.g., face is oriented 90° to the right of the electronic device).

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the enrollment of biometric features and the security of devices. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to improve biometric enrollment and to improve the security of devices. Accordingly, use of such personal information data enables users to better secure their data. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of biometric security, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide biometric data for audio-assisted enrolment of one or more biometric features. In yet another example, users can select to limit the length of time biometric data is maintained. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, devices can be secured based on non-personal information data or a bare minimum amount of personal information or publicly available information. 

What is claimed is:
 1. An electronic device, comprising: one or more biometric sensors; one or more processors operably connected to a first speaker and second speaker; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.
 2. The electronic device of claim 1, the one or more programs further including instructions for: after producing audio in a first audio production mode and while the electronic device remains in the first audio production mode: in accordance with a determination that the second orientation of the biometric feature does not meet the first enrollment criteria: continuing to produce audio in the first audio production mode.
 3. The electronic device of claim 1, the one or more programs further including instructions for: while the electronic device remains in the second audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the second orientation to a third orientation; and in accordance with a determination that the third orientation of the biometric feature meets a second enrollment criteria: storing second image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the third orientation.
 4. The electronic device of claim 1, wherein the first speaker and the second speaker are not in a fixed position relative to the one or more biometric sensors.
 5. The electronic device of claim 4, wherein producing audio in the first audio production mode includes modulating the audio of the first speaker and second speaker so that the audio continues to be generated so as to simulate audio being produced from the first location, wherein modulating the audio is based on a change in position of the first speaker and second speaker relative to the one or more biometric sensors.
 6. The electronic device of claim 4, wherein detecting a change in orientation of the biometric feature is based on one or more motion sensors, wherein the one or more motion sensors are in a fixed position relative to the first speaker and second speaker.
 7. The electronic device of claim 4, wherein the first location is in a direction perpendicular to a plane formed by the first speaker, the second speaker, and at least one of the one or more biometric sensors.
 8. The electronic device of claim 4, wherein the electronic device is operably connected to a third speaker and a fourth speaker and wherein producing audio in the first audio production mode includes: determining if the first speaker and second speaker are operable; and in accordance with determining that the first and second speakers are operable, foregoing producing audio using the third speaker and the fourth speaker.
 9. The electronic device of claim 1, wherein the first speaker and second speaker are in fixed positions relative to the one or more biometric sensors.
 10. The electronic device of claim 9, wherein producing audio in the first audio production mode includes foregoing modulating the audio of the first speaker and the second speaker based on a change in position of the biometric feature relative to the one or more biometric sensors.
 11. The electronic device of claim 1, wherein detecting a change in the orientation of the biometric feature is based on data from the one or more biometric sensors.
 12. The electronic device of claim 1, wherein producing audio in the first audio production mode includes: in accordance with a determination that the second orientation does not meet the first enrollment criteria and in accordance with a determination that a feedback criteria is met: producing audio in a third audio production mode, wherein audio produced in the third audio production mode is generated so as to simulate audio being produced from a third location that is not the location of the one or more biometric sensors, wherein the third location is different from the first location.
 13. The electronic device of claim 12, the one or more programs further including instructions for: in accordance with a determination that the second orientation does not meet the first enrollment criteria and in accordance with a determination that the feedback criteria is not met: remaining in the first audio production mode.
 14. The electronic device of claim 12, wherein the first enrollment criteria includes a target orientation and wherein the third location is determined based on a difference between the target orientation and the second orientation.
 15. The electronic device of claim 1, wherein producing audio in the first audio production mode includes producing a first tactile output corresponding to the first location.
 16. The electronic device of claim 1, the one or more programs further including instructions for: further in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: producing a second tactile output.
 17. The electronic device of claim 1, wherein the electronic device further includes a display, and wherein the one or more programs further include instructions for: while detecting that a biometric feature is in a first orientation, displaying, on the display, a biometric enrollment interface.
 18. The electronic device of claim 17, wherein producing audio in the first audio production mode includes displaying, as part of the biometric enrollment interface, a first visual output corresponding to the first location.
 19. The electronic device of claim 17, the one or more programs further including instructions for: further in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: displaying, on the display, a second visual output.
 20. The electronic device of claim 1, wherein producing audio in a first audio production mode includes: detecting, using the one or more biometric sensors, a distance a user is from the one or biometric sensors; and determining the first location based on the distance the user is from the one or more biometric sensors.
 21. The electronic device of claim 1, the one or more programs further including instructions for: prior to producing audio in the first audio production mode, detecting a user physical characteristic, wherein producing audio in a first audio production mode includes modulating the audio produced in the first audio production mode based on the user physical characteristic.
 22. The electronic device of claim 1, the one or more programs further including instructions for: receiving a request to access a restricted function of the electronic device; and in response to the request to access the restricted function of the device: in accordance with a determination that biometric authentication criteria has been met based on biometric data provided by the one or more biometric sensors, providing access to the restricted function of the device; and in accordance with a determination that biometric authentication criteria has not been met based on biometric data provided by the one or more biometric sensors, forgoing providing access to the restricted function of the device.
 23. The electronic device of claim 1, wherein: the biometric feature is at least a portion of a face; and the first image data obtained from the one or more biometric sensors includes biometric data associated with the at least a portion of the face.
 24. The electronic device of claim 23, wherein the first enrollment criteria includes a criterion that is satisfied when the biometric feature is oriented relative to the one or more biometric sensors in a predetermined manner.
 25. The electronic device of claim 1, wherein producing audio using the first audio production mode includes applying one or more functions selected from the group consisting of: a head-related transfer function, an interaural time difference function, and a cross cancellation function.
 26. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having one or more biometric sensors, and operably connected to a first speaker and a second speaker, the one or more programs including instructions for: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location.
 27. A method comprising: at an electronic device having one or more biometric sensors, and operably connected to a first speaker and a second speaker: while detecting that a biometric feature is in a first orientation, relative to the one or more biometric sensors, that does not meet a first enrollment criteria, producing audio in a first audio production mode, wherein audio produced in the first audio production mode is generated so as to simulate audio being produced from a first location that is not a location of the one or more biometric sensors and is not a location of the first speaker or the second speaker; while the electronic device remains in the first audio production mode: detecting a change in orientation of the biometric feature relative to the one or more biometric sensors from the first orientation to a second orientation; in accordance with a determination that the second orientation of the biometric feature meets the first enrollment criteria: storing first image data corresponding to the biometric feature from the one or biometric sensors captured while the biometric feature is in the second orientation; and producing audio in a second audio production mode, wherein audio produced in the second audio production mode is generated so as to simulate audio being produced from a second location that is not the location of the one or more biometric sensors and is not the location of the first speaker or the second speaker, wherein the first location is different from the second location. 